-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove qualify_min_const_fn
pass
#68940
Remove qualify_min_const_fn
pass
#68940
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
There's also some additional errors being reported in some UI tests that are unrelated to const-eval. I'll need to figure out what's going on here. |
☔ The latest upstream changes (presumably #68929) made this pull request unmergeable. Please resolve the merge conflicts. |
…-gate, r=oli-obk Return feature gate as a `Symbol` A minor refactoring that will be needed for rust-lang#68940. That PR is blocked on me changing the error comments in a whole lot of UI tests. r? @oli-obk
@ecstatic-morse any updates? |
r? @oli-obk totally forgot this exists |
let's wait for |
Closing this, but I think I'll get back to it in the near future. |
Having two MIR const-checking passes is confusing. This PR unifies
qualify_min_const_fn
andcheck_consts
.All checks from
qualify_min_const_fn
that were not already implemented incheck_consts
have been assigned a structured error. Unfortunately, this will require a lot of changes to expected test output. This is becausequalify_min_const_fn
bailed out after the first error was found, whilecheck_consts
reports all errors in the function.cc @rust-lang/wg-const-eval